test(ci): run native_proof_buffer_views per PR again after #8302 - #8321
Merged
Conversation
This was referenced Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#8302 restored the six
native_proof_buffer_viewsassertions that #8264recorded as baseline reds. Their
SUITE_EXCLUSIONSentries inscripts/ci_e2e_scope.pystayed behind.A stale exclusion does not produce a red build — it produces silence. The suite
keeps being skipped, so the coverage #8302 earned back never runs per PR. That
is exactly #7708's failure mode, and it is why #8264 wrote the entries as
self-invalidating in the first place.
Changes
native_proof_buffer_viewsentries fromSUITE_EXCLUSIONS.native_proof_buffer_viewsto the mapped set —--self-testrefuses asuite that is in neither list, which is how I caught that removing the
exclusions alone was not enough.
What is still excluded
The other two #8264 entries are genuinely red and keep their exclusions.
Re-checked at the merge commit of #8302:
native_proof_buffer_viewsshadow_slot_hygienecanonical_str_local_…) — stays excludedtyped_feedbacktyped_feedback_guards_direct_class_field_specialization) — stays excludedSo #8264 goes from eight red assertions to two.
Validation
python3 scripts/ci_e2e_scope.py --self-test— exit 0cargo test -p perry-codegen --test native_proof_buffer_views— 45/45 on this branchscripts/run_lint_gates.sh— all 48 lint-tier gates pass